Copyright: Copyright ¸ 1995, Novell, Inc. All rights reserved.


Adding TCP/IP Support
To add TCP/IP support

IMPORTANT:  You need access to the Windows 95 CAB files to successfully set up TCP/IP.

1. Click here  [image] to display the Network control panel.

2  Choose Add.

3  Choose Protocol.

4  Choose Add.

5  Choose Microsoft.

6  Choose TCP/IP.

7  Choose OK.

8  Configure the TCP/IP protocol as necessary for your network.

9  Choose OK.


Administrator Defaults

Overview

By specifying default values for configuration settings in an ADMIN.CFG file, you can simplify the installation of Client 32.  This configuration method is good for administrators who are familiar with the NET.CFG syntax, want to install and configure Client 32 at the same time, and need to configure settings that can't be configured using the System Policy Editor.

Admin Defaults Option

The ADMIN.CFG file must have the words "Admin Defaults" as its first line.  This is a new configuration option for Administrator Defaults.  The valid parameters for this option are OVERWRITE and VERSION.

OVERWRITE Parameter

The OVERWRITE parameter can be TRUE or FALSE.  TRUE means that all configuration settings in the ADMIN.CFG file are written to the registry.  FALSE means that the configuration settings in the ADMIN.CFG file are written to the registry only if they aren't already there.

VERSION Parameter

The VERSION parameter can be any number from 0 to 4,294,967,295.  If this number is greater than the Client 32 version number stored in the registry, the configuration settings in the ADMIN.CFG file are written to the registry and this number is stored as the new version number.  Otherwise, they aren't.  The first time Client 32 is installed, no version number is in the registry.  In this case, the Administrator Defaults are written to the registry, including the version number.

Admin Defaults Example

Admin Defaults

Overwrite = false

Version = 0

Notes

The ADMIN.CFG file must be in the same directory as the SETUP.EXE file that you run to install Client 32.

For information about the configuration settings that you can specify in the ADMIN.CFG file, see the Configuration Reference information in the NWCFG95.HLP file.


Automatic Client Upgrade

Automatic Client Upgrade (ACU) allows a network supervisor to centrally locate the Client 32 code on a file server.  At login time, the workstation can be updated with the Client 32 code the network supervisor has placed on the server.  This includes the ability to update to NetWare Client 32 for Windows 95 from the NETX, the VLM, or the Microsoft NetWare client.


Cabling Notes

See the network board manufacturer's documentation for cabling requirements.

Token ring network boards require a cable connection to the MAU before running the client software. Otherwise, the token ring LAN driver will not load.


Changing Installation Options
Change Installation Options

1  Choose Installation Options.

2  Set as many of the installation options as you want.

3  Choose OK.

Notes

The more options you set at this time, the fewer interactions are required when installing Windows 95 and Client 32 from the server.


Checking MSBATCH.INF

Compare the keys shown in the following MSBATCH.INF file with the ones generated by the INF Installer.  If any of the highlighted lines differ, click the highlighted line in the help file, read the note explaining the significance of the statement, and adjust your MSBATCH.INF file if necessary.

Notes

For more information about MSBATCH.INF parameters, see the Microsoft Windows 95 Resource Kit.

To set the values of Client 32 properties automatically during the installation, use the ADMIN.CFG file.

Example

[Setup]

Express=1

[Network]

clients=NOVELL32

protocols=NWLINK, NOVELLIPX32

[MSTCP]


Clients=NOVELL32

INF Installer should have added this line.  Remove any other clients.


Configure Client 32

1. (Conditional) If the Network control panel is not displayed, click here  [image] to display it.

2  Choose Novell NetWare Client 32.

3  Choose Properties.

4  Ensure the following properties are set correctly.

a  Preferred Server

For a bindery connection to the network, specify the NetWare server you want to attach to first.

b  Preferred Tree

For an NDS connection to the network, specify the Directory tree that you want to connect to.

c  Name Context

For an NDS connection to the network, specify the position, or context, in the Directory tree where your user object is located.  For example, to set your name context to the MNGT organizational unit in the MARKETING organization, type

OU=MNGT.O=MARKETING

5  Choose OK to save any changes to the properties.

6  Choose OK to exit the Network control panel and save your changes.

7. Click here [image] to start the System Configuration Editor.  Make sure VIPX.386 is not loaded in your SYSTEM.INI file.

Notes

For more information about configuring Client 32, see the configuration overview.


Configuring TCP/IP Support
Configure TCP/IP Support

1  Click here [image] to display the Network control panel.

2  Choose TCP/IP.

3  Choose Properties.

4  Make any necessary changes.

5  Choose OK.

6  Choose OK.

Notes

 Configure the TCP/IP protocol as necessary for your network.  NetWare/IP requires that DNS be configured either manually or via DHCP.


Configuring for a Real Mode (16 bit) NDIS Driver
Configure for Using a Real Mode (16-bit) NDIS Driver

1  Click here [image] to edit your AUTOEXEC.BAT file.

2  Ensure that your AUTOEXEC.BAT file executes the "NET START" command.

3  If Client 32 hangs, set the value for the Close Behind Ticks parameter to 0.

NOTE:  Setting the value of the Close Behind Ticks parameter to 0 decreases performance.  Therefore, do this only if you have a 16-bit NDIS driver and Client 32 hangs.


Contents
NetWare Client 32 for Windows 95 Help

Readme

Installing

Configuring

Troubleshooting

Tips and Tricks

Using the Network

What's New

To Print Help Topics

Trademarks

Disclaimer


Copy INFs from NetWare Client 32 Directory to Windows 95 Source Directories
Example

If the directory you created in Step 2 is C:\C32TEMP and your server install path is F:\WIN95, use the following commands to copy the .INF files.

COPY  C:\C32TEMP\*.INF	F:\WIN95

COPY  C:\C32TEMP\*.INF	F:\WIN95\INF

COPY  C:\C32TEMP\*.INF	F:\WIN95\SUWIN


Copying NETDEF.INF

Examples

If your CD-ROM drive is accessed as drive D: and your server install path is F:\WIN95, use the following commands to copy the NETDEF.INF file.

D:

CD \ENGLISH\ADMIN\BATCH

COPY  NETDEF.INF  F:\WIN95\NETDEF.INF

ATTRIB  -R  F:\WIN95\INF\NETDEF.INF

COPY  NETDEF.INF  F:\WIN95\INF\NETDEF.INF

ATTRIB  -R  F:\WIN95\SUWIN\NETDEF.INF

COPY  NETDEF.INF  F:\WIN95\SUWIN\NETDEF.INF

If you are installing from diskettes using drive A: and your server install path is F:\WIN95, use the following commands to copy the NETDEF.INF file after inserting the Admin disk in drive A:.

A:

CD \BATCH

COPY  NETDEF.INF  F:\WIN95\NETDEF.INF

ATTRIB  -R  F:\WIN95\INF\NETDEF.INF

COPY  NETDEF.INF  F:\WIN95\INF\NETDEF.INF

ATTRIB  -R  F:\WIN95\SUWIN\NETDEF.INF

COPY  NETDEF.INF  F:\WIN95\SUWIN\NETDEF.INF

Notes

The following are the key changes made to the NETDEF.INF file for NetWare Client 32 for Windows 95:

[NETWARE] Section

Original:

[NETWARE]

00000000=NETWARE3

00032600=NETWARE3

00040000=NETWARE4

Updated:

[NETWARE]

00000000=NOVELL32

00032600=NOVELL32

00040000=NOVELL32

[TYPICAL], [COMPACT], and [PORTABLE] Sections (only changed statements are shown)

Updated:

NetTrans=NWLINK,NOVELLIPX32

NetClient=NOVELL32

For NetWare/IP, NWIP should also be specified for NetTrans:

NetTrans=NWLINK,NOVELLIPX32,NWIP


Copying the INF Files

Notes

Copy the .INF files from the ENGLISH\ADMIN\BATCH directory of the Client 32 CD-ROM or from the BATCH directory of the Admin disk.  Copy them to the directory where you put all the files for Client 32.

Always copy the following files:

NWCLIENT.INF

NWTRANS.INF

NWLAYOUT.INF

For NetWare/IP support, copy the following file:

NWIP.INF

For SNMP support, copy the following file:

NWSERV.INF

If you want the Client 32 help integrated with the Windows 95 system help, edit the NWCLIENT.INF file and remove the semicolon (;) in front of the line that has OEM.CNT.  For more information about integrating the help, see Integrating Client 32 Help: Overview.


Creating MSBATCH.INF
Create an MSBATCH.INF File

1  Run BATCH.EXE.

2  (Optional) Fill in the Setup Information.

3  Remove Network Options.

4  Change the Installation Options.

5  (Optional) Select Optional Components.

6  Choose Done.

7  Save with a unique filename (such as C32BATCH.INF) in the directory that you specified as the server install path during Server-based Setup (for example, F:\WIN95).

8  Replace the existing MSBATCH.INF file with the file you just created.

a  Remove the read-only attribute from the existing MSBATCH.INF file.

b  Rename the existing MSBATCH.INF file.

c  Rename the file you just created to MSBATCH.INF.

For example:

ATTRIB -R MSBATCH.INF

RENAME MSBATCH.INF MSBATOLD.INF

RENAME C32BATCH.INF MSBATCH.INF

Notes

BATCH.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

BATCH.EXE can be run under Windows 3.x or Windows 95.

For more information about Batch Setup (BATCH.EXE), see the Microsoft Windows 95 Resource Kit.

You can also create or change the MSBATCH.INF file by hand.  For information on how to do this, see the Microsoft Windows 95 Resource Kit.


Customize Notes

After you choose Customize, the Network control panel is displayed.  You can use the Network control panel to do any of the following that you need to do to customize your workstation.

Configure Client 32

Set up optional features

Change the LAN driver for your network adapter.

Configure for a real mode (16 bit) NDIS driver

When you are finished, choose OK on the Network control panel and restart your computer.


Disabling the NetWare Logo Splash Screen

If you don't want the NetWare logo to be displayed when you start your workstation, add the following line to your NETWARE.INI file under the [Options] section:

DisableLogo=1

The NETWARE.INI file should be in the Windows folder (typically, C:\WINDOWS).


Disclaimer

Novell, Inc., makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of recreating lost data, the cost of any substitute equipment or program, or claims by any party other than you.

Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell.


Express=1

User input is not required or allowed during Windows 95 Setup.  To allow user input, specify "Express=0."


Files: Alphabetical List
Alphabetical List of Files

1252_UNI.001

3C503.COM

3C589.COM

3C5X9.COM

3C5X9.LAN

3C5X9.LDI

3C689.COM

3CTOKEN.COM

ADMIN.CFG

AM2100.COM

APPSNAP.DLL

APPSNAP.HLP

CALWIN16.DLL

CALWIN32.DLL

CEODI.COM

CLIENT32.NLM

CLNWIN16.DLL

CLNWIN32.DLL

CLNWINTH.DLL

CLXWIN16.DLL

CLXWIN32.DLL

CMSM.MSG

CMSM.NLM

CNE1500T.LAN

CNE1500T.MSG

CNE2.LAN

CNE2.MSG

CNE2000.LAN

CNE2000.MSG

CNE2100.LAN

CNE2100.MSG

CNE2_32.LAN

CNE2_32.MSG

CNE3200.LAN

CNE3200.MSG

CNTR2000.LAN

CNTR2000.MSG

DC21040.COM

ETHERTSM.MSG

ETHERTSM.NLM

F70ODI.COM

FDDITSM.MSG

FDDITSM.NLM

HOSTMIB.MSG

HOSTMIB.NLM

HP3AT16P.LAN

HP3AT16P.LDI

HPFEODI.COM

HPISAODI.COM

HPMCAODI.COM

IPX.NLM

LOCWIN16.DLL

LOCWIN32.DLL

LOGIN.DAT

LOGIN.MSG

LOGINW95.EXE

LOGINW95.HLP

LSL.COM

LSLC32.MSG

LSLC32.NLM

MADGEODI.COM

MSBATCH.INF

NAL.EXE

NAL.HLP

NALRES32.DLL

NALW95.EXE

NCPWIN16.DLL

NCPWIN32.DLL

NE1000.COM

NE1000.INF

NE1000.LAN

NE1500T.COM

NE15_21.INF

NE2.COM

NE2.INF

NE2000.COM

NE2000.INF

NE2100.COM

NE2_32.COM

NE2_32.INF

NE3200.COM

NE3200.INF

NESL.COM

NESL.MSG

NETDEF.INF

NETWARE.DRV

NETWIN16.DLL

NETWIN32.DLL

NIOS.VXD

NIOSLIB.DLL

NMR.NLM

NOVELLNP.DLL

NOVELNPR.DLL

NOVPP32.DLL

NTR2000.COM

NTR2000.INF

NWCALLS.DLL

NWCFG95.CNT

NWCFG95.HLP

NWCLIENT.INF

NWGDI.DLL

NWHOSTX.MIB

NWICFG.NLM

NWIP.INF

NWIP95.NLM

NWIPXSPX.DLL

NWLAYOUT.INF

NWLINK2.VXD

NWLOCALE.DLL

NWNET.DLL

NWOVER95.CNT

NWOVER95.HLP

NWPASSWD.DLL

NWPOPUP.EXE

NWPSRV.DLL

NWSERV.INF

NWSETUP.DLL

NWSETUP.INI

NWSHELLX.DLL

NWSIPX32.DLL

NWSIPX32.NLM

NWTIPS95.CNT

NWTIPS95.HLP

NWTRANS.INF

NWTSG95.CNT

NWTSG95.HLP

NWUSE95.CNT

NWUSE95.HLP

OC32T164.LAN

OC32T164.LDI

ODI3COM.INF

ODI3COMT.INF

ODIALLIE.INF

ODIAMD.INF

ODIARC.INF

ODIAST.INF

ODIBOCA.INF

ODICABLE.INF

ODICOGNT.INF

ODICPQ.INF

ODIDCA.INF

ODIDEC.INF

ODIDELL.INF

ODIEXOS.INF

ODIFARA.INF

ODIFLEX.INF

ODIHP.INF

ODIIBMTR.INF

ODIINTEL.INF

ODIKING.INF

ODILNKSY.INF

ODILOAD.VXD

ODIMADGE.INF

ODIMHZ.INF

ODIMICRO.INF

ODIMITRO.INF

ODINCR.INF

ODINSUP.INF

ODINSUP.SYS

ODIOLI.INF

ODIPAGE.DLL

ODIPCN2.INF

ODIPROT.INF

ODIPURE.INF

ODIRACAL.INF

ODISILC.INF

ODISMC.INF

ODISMCTR.INF

ODISMC32.INF

ODISVEC.INF

ODISYS.INF

ODITCC.INF

ODITDKP.INF

ODITOSH.INF

ODITULIP.INF

ODIUB.INF

ODIXIR.INF

ODIZNYX.INF

PC32MLID.LAN

PC32MLID.MSG

PCNTNW.COM

PEDOSODI.COM

PHASERS.WAV

PIDOSODI.COM

PRTWIN16.DLL

PRTWIN95.DLL

README.NAL

README.TXT

ROUTE.COM

RFC1514.MIB

SETUP.EXE

SETUPNW.CNT

SETUPNW.HLP

SMC8000.COM

SMC8000.LAN

SMC8000.LDI

SMC80PC.COM

SMC8100.COM

SMC8100.LAN

SMC8100.LDI

SMC8232.COM

SMC8332.COM

SMC9000.COM

SMCPWR.COM

SNMP.MSG

SNMP.NLM

SNMPDLL.DLL

SNMPIPX.EXE

SNMPUDP.EXE

SPX_SKTS.NLM

SROUTE.MSG

SROUTE.NLM

SUPWIN16.DLL

TCCARC.COM

TCE32ESW.COM

TCE32MCW.COM

TCE32PCW.COM

TCNSW.COM

TCTOKSH.COM

TLI_SPX.DLL

TLI_WIN.DLL

TOKENTSM.MSG

TOKENTSM.NLM

TRXNET.COM

UNI_1252.001

UNI_COL.001

UNI_MON.001

VMLID.NLM


Files: By Folder
List of Files by Folder

\Novell\Client32

\Novell\Client32\Install

\Novell\Client32\Nls\language

\Novell\Nwclient

\Windows

\Windows\Help

\Windows\Inf

\Windows\Nls\language

\Windows\System

Other


Files: By Function
List of Files By Function

NetWare/IP Files

SNMP Files

Host Resources MIB Files

LAN Driver Files

Help Files

Provider Files

Installation Files


Files: LAN Driver
LAN Driver Files

32-bit LAN Drivers

3C5X9.LAN

CNE1500T.LAN

CNE2.LAN

CNE2000.LAN

CNE2100.LAN

CNE2_32.LAN

CNE3200.LAN

CNTR2000.LAN

HP3AT16P.LAN

MADGEODI.LAN

NE1000.LAN

OC32T164.LAN

SMC8000.LAN

SMC8100.LAN

16-bit LAN Drivers

3C503.COM

3C589.COM

3C5X9.COM

3C689.COM

3CTOKEN.COM

AM2100.COM

CEODI.COM

DC21040.COM

F70ODI.COM

HPFEODI.COM

HPISAODI.COM

HPMCAODI.COM

MADGEODI.COM

NE1000.COM

NE1500T.COM

NE2.COM

NE2000.COM

NE2100.COM

NE2_32.COM

NE3200.COM

NTR2000.COM

PCNTNW.COM

PEDOSODI.COM

PIDOSODI.COM

SMC8000.COM

SMC80PC.COM

SMC8100.COM

SMC8232.COM

SMC8332.COM

SMC9000.COM

SMCPWR.COM

TCCARC.COM

TCE32ESW.COM

TCE32MCW.COM

TCE32PCW.COM

TCNSW.COM

TCTOKSH.COM

TRXNET.COM


Files: Other Folders

List of Files in Other Folders

SNMP management station files:

RFC1514.MIB

NWHOSTX.MIB


Files: Overview
Client 32 Files

Beta Note:  This information is still being compiled.  It is currently incomplete.  It is also subject to change.

Alphabetical list of files

List of files by folder

List of files by CD-ROM location

List of files by function

List of third-party LAN drivers


Files: \Novell\Client32
List of Files in the \Novell\Client32 Folder

CLIENT32.NLM

CMSM.NLM

CNE2000.LAN

CNE3200.LAN

ETHERTSM.NLM

FDDITSM.NLM

IPX.NLM

LGNW9532.DLL

LOGINW95.EXE

LSLC32.NLM

NMR.NLM (if NMR is installed)

NWIP95.NLM (if NetWare/IP is installed)

NWPOPUP.EXE

NWSIPX32.NLM

PC32MLID.LAN

PHASERS.WAV

README.TXT

SETUPNW.CNT

SETUPNW.HLP

SPX_SKTS.NLM

SROUTE.NLM

TOKENTSM.NLM

VMLID.NLM


Files: \Novell\Client32\Install
List of Files in the \Novell\Client32\Install Folder

ADMIN.CFG

NET2REG.LOG


Files: \Novell\Client32\Nls\language
List of Files in the \Novell\Client32\Nls\language Folder

LOGIN.DAT

LOGIN.MSG

Notes

The name of this folder varies depending on the language being used.  For English, the name is "\Novell\Client32\Nls\English."


Files: \Novell\Nwclient
List of Files in the \Novell\Nwclient Folder

LSL.COM

N16ODI.COM

NE2000.COM

NESL.COM


Files: \Windows
List of Files in the \Windows Folder

LSL.COM


Files: \Windows\Help
List of Files in the \Windows\Help Folder

LOGINW95.HLP

NWCFG95.HLP

NWOVER95.HLP

NWTIPS95.HLP

NWTSG95.HLP

NWUSE95.HLP

Note:  Each of these help files might also have files with the following file types associated with them:

CNT

FTS

GID


Files: \Windows\Inf
List of Files in the \Windows\Inf Folder

NE1000.INF

NE15_21.INF

NE2.INF

NE2000.INF

NE2_32.INF

NE3200.INF

NETDEF.INF

NTR2000.INF

NWCLIENT.INF

NWIP.INF

NWLAYOUT.INF

NWSERV.INF

NWTRANS.INF

ODINSUP.INF


Files: \Windows\Nls\language
List of Files in the \Windows\Nls\language Folder

NOVELNPR.DLL

Notes

The name of this folder varies depending on the language being used.  For English, the name is "\Windows\Nls\English."


Files: \Windows\System
List of Files in the  \Windows\System Folder

CALWIN16.DLL

CALWIN32.DLL

CLNWIN16.DLL

CLNWIN32.DLL

CLNWINTH.DLL

CLXWIN16.DLL

CLXWIN32.DLL

LOCWIN16.DLL

LOCWIN32.DLL

NCPWIN16.DLL

NCPWIN32.DLL

NETWARE.DRV

NETWIN16.DLL

NETWIN32.DLL

NIOS.VXD

NIOSLIB.DLL

NOVELLNP.DLL

NOVPP32.DLL

NWCALLS.DLL

NWDRVLGO.BMP

NWGDI.DLL

NWIPXSPX.DLL

NWLINK2.VXD

NWLOCALE.DLL

NWNET.DLL

NWPASSWD.DLL

NWPSRV.DLL

NWSETUP.DLL

NWSHELLX.DLL

NWSIPX32.DLL

ODILOAD.VXD

ODINSUP.SYS

ODIPAGE.DLL

PRTWIN16.DLL

PRTWIN95.DLL

SUPWIN16.DLL

TLI_SPX.DLL

TLI_WIN.DLL


HOSTMIB.NLM File

This file implements the standard Host Resources MIB as defined by the Internet Engineering Task Force (IETF) and Novell's NetWare Host Resources Extensions MIB.  Its basic purpose is to allow SNMP management software to manage the physical resources of a client workstation.


Installation Complete

To use NetWare Client 32 for Windows 95, choose Reboot.  When your workstation reboots, Client 32 starts automatically.

To use Windows 95 before restarting your workstation, choose Return to Windows.  When you're ready to use Client 32, shut down Windows 95 and restart your workstation.

To add optional features to your configuration or to change Novell NetWare Client 32 properties, choose Customize.  Use the Network control panel to Add the protocols or services or to change the Properties that you want, then choose OK and restart your workstation.

To view this help topic, choose Help.  You can view instructions about adding NetWare/IP, SNMP, NMR, or the Host Resources MIB or configuring NetWare Client 32 by using this help file.


Installation Overview

There are four methods of installing NetWare Client 32 for Windows 95.

Setting up a server with the Windows 95 and Client 32 files so that they can be installed at the same time from the server.

Installing interactively at the workstation after Windows 95 has been installed.

Installing using the Custom Setup Option of Windows 95 Setup.

Using the Automatic Client Upgrade feature.


Installation Screen

To install NetWare Client 32 for Windows 95, choose Start.  Any existing NetWare clients are removed and Client 32 is added.

IMPORTANT:  If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

To quit the installation, choose Cancel.

To see this help topic, choose Help.  There are also many other help topics available about installing and configuring Client 32.

To see README information, choose View Readme.


Installing (Contents)
Installing Client 32

Overview

Preparing for Installation

Option 1:  Installing Using a Server-Based Windows 95 Install

Option 2:  Installing on a Workstation that Already Has Windows 95 Installed

Option 3:  Installing Using Custom Windows 95 Setup

Automatic Client Upgrade

Installing Additional Protocols and Optional Features

Removing


Installing Interactively

To set up NetWare Client 32 for Windows 95

IMPORTANT:  If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

1  Run the installation program, SETUP.EXE.

2  Choose Yes or No to respond to the Novell License Agreement.

3  Choose Start to install NetWare Client 32 for Windows 95.

4  (Conditional)  If you are prompted to select a network adapter, choose the one that matches your hardware.

5  (Conditional) If you don't need to customize your installation, choose Reboot.

OR

(Conditional) If you want optional features or need to configure your workstation, choose Customize.

Notes

You can put the Client 32 files on a NetWare server, map a drive to the directory where you put them, and run SETUP.EXE from the mapped drive.  It is better to map a drive than it is to use the Universal Naming Convention (UNC) name because the help is not always available if you use the UNC name.


Installing Using a Server-based Windows 95 Install
Option 1: Installing Using a Server-Based Windows 95 Install

Overview

Step 1: Run Server-based Setup (NETSETUP.EXE).

Step 2: Put all the Client 32 files into a directory.

Step 3: Remove all the .INF files from the directory in Step 2.

Step 4: Copy the .INF files from the BATCH directory to the directory in Step 2.

Step 5: Create an MSBATCH.INF file.

Step 6: Run the INF Installer (INFINST.EXE) to add Client 32 to the MSBATCH.INF file.

Step 7: Check the MSBATCH.INF file.

Step 8: Copy the NETDEF.INF file from the BATCH directory to the Windows 95 source directory on the NetWare server and its INF and SUWIN subdirectories.

Step 9: Run Windows 95 Setup (SETUP.EXE MSBATCH.INF).


Integrate Client 32 Help: Can't Display Help
Windows 95 couldn't open the WINDOWS.HLP file.

Use the Windows 95 Find function to find the WINDOWS.HLP file and open it.  If you renamed the WINDOWS.HLP file, find and open it under its new name.  If you erased this file or didn't install the Windows 95 help, you can't integrate the Client 32 help with the Windows 95 system help.


Integrate Client 32 Help: Can't Reinitialize Help
The following command did not complete successfully:

WINHELP  -G  WINDOWS.HLP

This command is used to reinitialize the Windows 95 help in order to update the WINDOWS.GID file with information about the Client 32 help.

The most likely reasons that the command failed are that Windows 95 couldn't find the WINHELP.EXE file or that it couldn't find the WINDOWS.HLP file.  If you know where these files are, try entering the command using the full path of each file.  For example:

C:\WINDOWS\WINHELP.EXE  -G  C:\WINDOWS\HELP\WINDOWS.HLP

If this doesn't work, you might also try forcing Windows 95 to reinitialize the Windows 95 help by deleting the WINDOWS.GID file.  The WINDOWS.GID file is a hidden file.  Usually, it is in the Windows Help folder (typically, C:\Windows\Help).  Windows help recreates the WINDOWS.GID file if it is not found when Windows help tries to display the WINDOWS.HLP file.


Integrate Client 32 Help: How To
Integrate Client 32 Help

1  Click here [image] to see if the Client 32 help is already integrated.

2  If [image] Novell NetWare Client 32 is displayed in the Contents tab of Help Topics, the Client 32 help is already integrated with the Windows 95 system help, and you're done with this task.  Otherwise, continue.

3  Compare the OEM.CNT file in your Windows Help folder (typically, C:\Windows\Help) with the OEM.CNT file that is shipped with Client 32 (in the English directory of the CD-ROM).

4  (Conditional)  If the OEM.CNT file in your Windows Help folder is different from the OEM.CNT file that is shipped with Client 32, append the Client 32 OEM.CNT file to the one in your Windows Help folder.

5  (Conditional)  If there isn't an OEM.CNT file in your Windows Help folder, copy the Client 32 OEM.CNT file to your Windows Help folder.

6  (Recommended) Click here [image] to print this help topic.

7  Click here [image] to integrate the Client 32 help.

This might take several seconds, and this help file will no longer be displayed.  To verify that the Client 32 help is integrated, continue with the following steps.

8  Choose Cancel to close Help Topics: Windows Help.

9  Choose Start on the taskbar.

10  Choose Help.

11  See Step 2.


Integrating Client 32 Help: Overview
Integrating Client 32 Help

When the Client 32 help is integrated with the Windows 95 system help, you can display the Client 32 help by choosing Start on the taskbar, then choosing Help, and, finally, by double-clicking Novell NetWare Client 32.

The key to this integration is the OEM.CNT file.  If this file doesn't already exist in your Windows Help folder (typically, C:\Windows\Help), the Client 32 installation copies this file there.  In which case, the Client 32 help is integrated with the Windows 95 help.  If you don't want this, rename or erase the OEM.CNT file.

If your workstation already has an OEM.CNT file, you can append the OEM.CNT file that is shipped with Client 32 to your existing OEM.CNT file in order to integrate the Client 32 help.


Integrating Help

Overview

How to


LOGINW95.HLP File

This is the help file for the graphical login utility.  It has a link to the SETUPNW.CNT file.


LSL.COM File

This is the 16-bit Link Support Layer (LSL) program.  It is used with 16-bit ODI LAN drivers.  It is loaded in the AUTOEXEC.BAT file before any other Client 32 programs.


Miscellaneous Notes

We support the Windows 95 built-in implementations of Server Messenger Blocks (SMB), Winsock, Named Pipes, and NetBIOS.

The NetWare for Windows 95 IPX protocol stack works with the WSOCK32.DLL that comes with Windows 95.

If you check Reconnect at logon when you map network drives, you can have the same drive mappings each time you log in even without login script processing.

NetWare Client 32 for Windows 95 can coexist with the [Microsoft] Client for Microsoft Networks.


NET.CFG Requirements for Smart Defaults

NET.CFG Options

The following NET.CFG options are moved to the registry.  Other NET.CFG options are ignored.  Obsolete NET.CFG parameters are also ignored.

DESKTOP SNMP

LINK SUPPORT

NETWARE DOS REQUESTER

NIOS

NWIP

PROTOCOL IPX

RESOURCES

NET.CFG Syntax

The following syntax rules must be obeyed:

The NET.CFG options must be spelled as shown above.

The NET.CFG options are not case sensitive.

A line cannot be more than 512 characters long.

Spaces, tabs, and equal signs can be used to separate parameters and values.

Valid values must be specified for the parameters.

NET.CFG Location

If a current Novell NetWare client is running, its NET.CFG file is used.

Otherwise, the first NET.CFG file found in the following folders is used:

\NOVELL\CLIENT32

\NWCLIENT

\NET\BIN

Otherwise, the first NET.CFG file found in the path name is used.


NETWARE.DRV File

The NetWare Device Driver, which is provided for backward compatibility with 16-bit Windows applications that are NetWare aware.


NWCFG95.HLP File

This is the help file for Client 32 configuration.  It has links to the NWOVER95.HLP, SETUPNW.HLP, SETUPNW.CNT, and NWTSG95.HLP files.


NWHOSTX.MIB File

This Management Information Base (MIB) defines extensions to the Host Resources MIB -- for Novell NetWare servers.

Source location:  ADMIN disk, NMS subdirectory.

Destination location:  SNMP management station.  See the instructions for your SNMP management software for details.

Notes

Must be manually copied to the appropriate destination.


NWOVER95.HLP File

This is the help file for Client 32 overview information.  It has links to the NWCFG95.HLP and SETUPNW.HLP files.


NWSHELLX.DLL File

Provides shell extensions for Windows 95.


Network Board Installation Notes

For information on installing the network board, see the manufacturer's documentation.

NetWare Client 32 for Windows 95 supports both Open Data-Link Interface (ODI) and Network Driver Interface Specification (NDIS) drivers.


No: Non-Disclosure Agreement
No

If you choose No, that's the end.  Ignore all the rest of the instructions.  You can't use NetWare Client 32 for Windows 95.


Novell ODINSUP Removal
Do not remove any instances of Novell ODINSUP from the Network control panel unless you know which one belongs to which ODI adapter.  There is a one-to-one mapping.  You cannot just remove any of them.  Novell ODINSUP is automatically removed when the adapter is removed, but not until after the Network control panel is closed.  Also, removing Novell ODINSUP removes Client 32 if there is only one adapter in use.


ODINSUP Overview

The ODI NDIS support module (ODINSUP) is an Open Data-Link Interface (ODI) protocol stack that interfaces between NDIS and ODI LAN drivers.

ODINSUP provides ODI support for NDIS protocols.  This enables you to use Microsoft networking components with ODI LAN drivers.  For example, using ODINSUP allows you to use the Client for Microsoft Networks with an ODI driver.  Another example would be using ODINSUP to enable you to use the Microsoft TCP/IP protocol with an ODI driver.


OEM.CNT File

This file can be used to integrate the Client 32 help with the Windows 95 system help.

For more information, see Integrating Client 32 Help: Overview.


Open Beta Notes
README

Please refer to the README.TXT file, which is on the Setup disk in the NLS\ENGLISH directory or, after Client 32 is installed, in the Novell\Client32 directory on your hard disk.


Option 3:  Installing Via Custom Windows 95 Setup

To install NetWare Client 32 for Windows 95 using Windows 95 Custom Setup

1  Run Windows 95 Setup.

2  Select Custom when the Windows 95 Setup Wizard displays the Setup Options.

When presented with your Network Configuration:

1  (Conditional) If you have a NetWare client installed, remove it.

2  Add NetWare Client 32 for Windows 95.

a  Choose Add.

b  Choose Client.

c  Choose Add.

d  Choose Have Disk.

e  Specify the path for the NetWare Client 32 for Windows 95 files.

f  Choose OK.

3  Configure NetWare Client 32 for Windows 95.

a  Choose Novell NetWare Client 32.

b  Choose Properties.

c  Make sure the information for "Preferred server," "Preferred tree," "Name context," and "First network drive" are correct.

d  Do any other configuration.


PC32MLID.LAN File

The PC32MLID.LAN file is a shim between the 16-bit DOS ODI specification and the 32-bit C-ODI specification.  It acts like a 32-bit LAN driver, but it uses 16-bit LAN drivers to transmit and receive network data.  It must be used if you are using 16-bit DOS ODI LAN drivers with Client 32.

The PC32MLID.LAN driver must be loaded after LSLC32.NLM and before IPX.NLM.

PC32MLID.LAN is installed when a 16-bit ODI LAN driver is installed.  It is loaded as part of the boot-up process.


PHASERS.WAV File

A wave file for the FIRE PHASERS login script command.  This file has the phaser sound.


Preparing Your Workstation Hardware

The following checklist can help you prepare your workstation for installing Client 32.

Prerequisites

PC with an Intel (or compatible) 80386 or above processor

A hard disk with 6 MB of free storage space

6 MB or more of RAM

A network board installed in your workstation

For more information, see Network Board Installation Notes.

A cable connection to the network

For more information, see Cabling Notes.


Preparing Your Workstation Software

The following checklist can help you prepare your workstation software for installing NetWare Client 32 for Windows 95.  If you are installing the client on a new workstation, first prepare your workstation hardware, and then return to this section.

Prerequisites

You must be running Windows 95.

The NetWare Client 32 for Windows 95 CD-ROM or diskettes.

If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

Notes

The following network components are not compatible with NetWare Client 32 for Windows 95::

[Microsoft] Client for NetWare Networks

[Microsoft] File and printer sharing for NetWare Networks

[Microsoft] Service for NetWare Directory Services

Novell NetWare (Workstation Shell 3.x [NETX])

Novell NetWare (Workstation Shell 4.0 and above [VLM])

Novell IPX ODI Protocol

Note:  This is the 16-bit module for the NETX and VLM clients.  Client 32 uses the IPX 32-bit Protocol for Novell NetWare Client 32.

These network components conflict with Client 32.  If any of these network components is installed, the Client 32 installation program detects the conflict and removes the conflicting network component.


Preparing for Installation

Preparing Your Workstation Hardware

Preparing Your Workstation Software


protocols=NWLINK, NOVELLIPX32

INF Installer should have added this line.  Add NWLINK if it is missing.  Remove any other protocols except NWIP.

For NetWare/IP:

The Protocols statement must be:

protocols=NWLINK, NOVELLIPX32, NWIP

Make sure the MSTCP protocol is not listed, because NetWare/IP automatically loads the MSTCP protocol.


Putting Files in a Directory
Putting the Client 32 Files into a Directory

Notes

This directory can be on the local hard disk, the NetWare server, or any other location accessible to the INF installer (INFINST.EXE).

Copy the files from the ENGLISH directory of the Client 32 CD-ROM or from the Client 32 diskettes.

Do not copy the files in the ENGLISH\ADMIN directory of the Client 32 CD-ROM or on the Admin disk to the directory at this point.


RFC1514.MIB File

Definitions for the Host Resources Management Information Base (MIB).

Source location:  ADMIN disk, NMS subdirectory.

Destination location:  SNMP management station.  See the instructions for your SNMP management software for details.

Notes

Must be manually copied to the appropriate destination.


ROUTE.COM File

The NetWare source routing driver (the ROUTE.COM file) enables communication across IBM token-ring network bridges.  It is used only for 16-bit ODI LAN drivers.

ROUTE.COM is loaded in the AUTOEXEC.BAT file after the 16-bit ODI LAN driver.  There must be a ROUTE command for each frame type that you want to use source routing.

The NetWare server also needs to load source routing (ROUTE.NLM).


Reboot Notes

When your workstation reboots, Client 32 starts automatically.


Remove Client 32

To remove NetWare Client 32 for Windows 95

1  Click here  [image] to display the Network control panel.

2  Choose Novell NetWare Client 32.

3  Choose Remove.

4  Remove any other Client 32 networking components (such as the Novell ODINSUP component and the IPX 32-bit Protocol for Novell NetWare Client 32) in the same way.

5  Choose OK.

6  Choose No.

7  Remove the Client 32 files.  For lists of Client 32 files, see Client 32 Files.


Remove NetWare Client

To remove a NetWare client

1  Choose the name of the client.

The name should be one of the following:

Client for NetWare Networks

Novell NetWare (Workstation Shell 3.X (NETX))

Novell NetWare (Workstation Shell 4.0 and above (VLM))

2  Choose Remove.

Note

You do not need to exit the Network control panel or restart your computer at this point.


Removing INF Files

Notes

Rename or erase all the files with an extension of .INF in the directory where you put all the files for NetWare Client 32 for Windows 95.


Removing Network Options
Remove Network Options

1  Choose Network Options.

2  Uncheck any protocols, services, clients, or other options that are checked.

3  Check IPX/SPX compatible protocol, which is listed under Available Protocols.

4  Choose OK.

5  Choose No--you don't want the default protocols.


Restart Your Computer

1  Remove any diskettes from the diskette drive (if you haven't already).

2. Choose Yes on the System Settings Change window.

Notes

The System Settings Change window asks you if you want to restart your computer now.  Occasionally, this pop-up might be partially or totally hidden.  If you don't see it, minimize or close windows until you do.

If the System Settings Change window is not displayed, restart your computer by doing the following:

1  Choose Start on the taskbar.

2. Choose Shut Down.

3. Choose Restart the computer?

4. Choose Yes.

The following error might be displayed when trying to map a search drive during login.

Insufficient memory is available to add the variable to the path environment in the mapping: [INS S16: SERVER\VOLUME\PATH

This is a known problem, and it is being addressed.


Running NETSETUP.EXE
Run Server-based Setup

1  (Conditional) Log in to the NetWare server and map a network drive to the volume from which you want users to install Windows 95 and Client 32.

2  Run NETSETUP.EXE under Windows 95.

NETSETUP.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

3  Set the server install path to the directory on the NetWare server from which you want users to install Windows 95--F:\WIN95, for example.

a  Choose Set Path.

b  Enter the path.

c  Choose OK.

4  Install the Windows 95 source files to the server install path.

a  Choose Install.

b  Choose Local hard drive.

c  Enter the path that has the Windows 95 cabinet files (*.CAB) as the Path to install from--F:\WIN95CAB, for example.

d  Choose OK.

e  Respond to the Create Default prompt.  Choose either option.

f  Follow the instructions for responding when any other prompts are displayed.

g  Choose Exit after the installation is complete.

Notes

Server-based Setup (NETSETUP.EXE) must be run under Windows 95.  It cannot be run successfully under any other workstation operating system.

Server-based Setup (NETSETUP.EXE) extracts the Windows 95 source files from the cabinet (*.CAB) files in the source directory (Path to install from) and places the source files into the destination directory (Path to install to).

Running Server-based Setup (NETSETUP.EXE) might take 15 to 45 minutes depending on the performance of your workstation and the network.

For more information about Server-based Setup (NETSETUP.EXE), see the Microsoft Windows 95 Resource Kit.


Running Windows 95 Setup
Install Windows 95 and Client 32

1  (Conditional) Log in to the NetWare server and map a network drive to the volume that has the Windows 95 and Client 32 files.

2  Run SETUP.EXE with MSBATCH.INF as the first parameter.

For example:  SETUP  F:\WIN95\MSBATCH.INF

Notes

Specify the complete path of the MSBATCH.INF file.

Use the SETUP.EXE program that is in the directory that you specified as the server install path during Server-based Setup (for example, F:\WIN95).

For more information about Windows 95 Setup (SETUP.EXE) including the workstation requirements for running SETUP.EXE, see the Microsoft Windows 95 Resource Kit.


Running the INF Installer
Run the INF Installer

1  (Conditional) Log in to the NetWare server and map a network drive to the volume where you installed the Windows 95 files using Server-based Setup (NETSETUP.EXE).

2  Run the INF Installer (INFINST.EXE).

3  Choose Set path.

4  Enter the Server Path.

Specify the directory on the server where the Windows 95 files are located (for example, F:\WIN95).

5  Choose Install INF.

6  Choose NWCLIENT.INF.

The NWCLIENT.INF file is in the directory where you put all the Client 32 files.

7  Choose OK.

Important:  Do not keep the existing NETWARE.DRV file even if it is newer than the NETWARE.DRV file that is shipped with Client 32.  Choose NO in response to the Version Conflict message.

Important:  It is strongly recommended that you not skip files.  If the INF Installer cannot find a file, specify the path where you think the file is.  For example, try the directory where you put all the Client 32 files.

8  Respond to any messages that are displayed as the INF Installer runs.

9  Choose Exit when finished.

Notes

INFINST.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

The NWCLIENT.INF file must be in the directory where you put all the Client 32 files.  You should already have copied it there from the ENGLISH\ADMIN\BATCH directory on the NetWare Client 32 for Windows 95 CD-ROM or from the BATCH directory on the Admin disk.

The INF Installer installs all the .INF files that are in the same directory as the .INF file you specify.  Only the .INF files that you want installed should be in that directory.

The INF Installer (INFINST.EXE) must be run under Windows 95.  It cannot be run successfully under any other workstation operating system.


SROUTE.NLM File

This is the source route NLM program.  It is designed to provide source routing support for Client 32.

Source routing enables communication across IBM token-ring network bridges.  SROUTE.NLM is the 32-bit replacement for ROUTE.COM.


Selecting a Network Adapter
Select a Network Adapter

1  Choose Novell or the manufacturer of your network adapter.

2  Choose the network adapter that matches your hardware.

For example, choose NE2000 Compatible if you have an NE2000-compatible network adapter.

3  Choose OK.

Notes

The Novell IPX Monolithic Driver is not supported.

There should be a matching Novell ODINSUP component for each ODI LAN driver.  It is installed automatically.  For more information, see the ODINSUP Overview.

Generally, you should not remove Novell ODINSUP from the Network control panel unless it is the only ODINSUP in the system.


Server-based Setup Overview
Overview of Installation Option 1

If you need to install Windows 95 and Client 32 on multiple workstations, investigate installing Client 32 using a server-based Windows 95 install.  This installation option requires some preparation, but can simplify the installation on each workstation.  User interaction for the Client 32 portion of the installation can be completely eliminated.  User interaction for the Windows 95 portion of the installation can be kept to a minimum.

The preparation involves using some Windows 95 utility programs.  These programs are available only on the Windows 95 CD-ROM and not on the Windows 95 diskettes.  As of this writing, the programs are also available from Microsoft on the Internet.  The programs prepare the Windows 95 and Client 32 files on a file server, so that Windows 95 and Client 32 can be installed at the same time.  During the installation, the files are copied from the server to the workstation.


Setting Up NMR
Set Up NMR

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up the Network Management Responder (NMR).

1. Click here  [image] to display the Network control panel.

2  Choose Add.

3  Choose Service.

4  Choose Add.

5  Choose Novell.

6  Choose NetWare Network Management Responder for Novell Client 32.

7  Choose OK.

Notes

NMR is an optional feature of NetWare Client 32 for Windows 95.


Setting Up NetWare/IP
Set Up NetWare/IP

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up NetWare/IP.

1. Click here  [image] to display the Network control panel.

2  Choose Add.

3  Choose Protocol.

4  Choose Add.

5  Choose Novell.

6  Choose Novell NetWare/IP protocol.

7  Choose OK.

8  Configure NetWare/IP.

9  (Conditional) If TCP/IP isn't already configured, configure it.

Notes

NetWare/IP requires that the TCP/IP protocol stack be Transport Driver Interface (TDI)-compliant.


Setting Up Optional Features
Installing Optional Features

Installing the Host Resources MIB

Installing NetWare/IP

Installing NMR

Installing SNMP

Integrating Help


Setting Up SNMP
Set Up SNMP

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up SNMP.

1. Click here  [image] to display the Network control panel.

2  Choose Add.

3  Choose Service.

4  Choose Add.

5  Choose Novell.

6  Choose Novell SNMP Agent.

7  Choose OK.

8  (Optional) Configure SNMP.

9  (Conditional) If TCP/IP isn't already installed, add it.


Setting Up the Host Resources MIB
Set Up the Host Resources MIB

IMPORTANT:  You need access to the NetWare Client 32 for Windows 95 files to successfully set up the Host Resources MIB.

1. Click here  [image] to display the Network control panel.

2  Choose Add.

3  Choose Service.

4  Choose Add.

5  Choose Novell.

6  Choose Host Resources MIB for Novell Client 32.

7  Choose OK.

8  (Optional) Configure the Host Resources MIB.

9  (Conditional) If you haven’t already installed TCP/IP, install it.

Notes

There are two MIB files that need to be copied to the network management station:

NWHOSTX.MIB

RFC1514.MIB

The Host Resources MIB is an optional feature of Client 32.

The Host Resources MIB for Novell Client 32 is compatible only with the Novell SNMP Agent  It is not compatible with any other SNMP agent


Smart Defaults

During the installation of Client 32, the following settings are checked and used if applicable.

If Microsoft's Client for NetWare Networks is installed, any values that have been specified for settings that are applicable to Client 32 are preserved.

If there is a NET.CFG file, all applicable NET.CFG entries are preserved by moving them to the registry.  Some parameters are not used or needed for Client 32, so they are not moved to the registry.  In other words, a subset of all NET.CFG parameters are moved to the registry.

NetWare Client 32 for Windows 95 does not include its own TCP/IP protocol stack.  Therefore, any existing TCP/IP parameters are not moved from the NET.CFG file to the registry.

If there is an ADMIN.CFG file, the parameters specified therein are moved to the registry.  For more information, see Administrator Defaults.

Notes

Any time the Client 32 installation program (SETUP.EXE) runs, the Smart Defaults function also runs.  Therefore, you can use Smart Defaults with the following installation methods:

Option 1:  Installing Using a Server-Based Windows 95 Install

Option 2:  Installing on a Workstation that Already Has Windows 95 Installed

Automatic Client Upgrade

For more information about moving parameters from a NET.CFG file to the registry, see NET.CFG Requirements for Smart Defaults.

A log file containing details about what parameters were written to the registry is created.  This log file is NET2REG.LOG.  It is written to the folder where the NET.CFG file is located.


Source Folder Notes

If you choose Browse on the Install From Disk pop-up window, the Open pop-up window displays .INF filenames as well as folders.  The .INF file for NetWare Client 32 for Windows 95 is NWCLIENT.INF.  Select the folder that has the NWCLIENT.INF file using the Open pop-up and choose OK.  The path of the folder that contains the NWCLIENT.INF file is displayed on the Install From Disk pop-up.  Do not add NWCLIENT.INF to the path.  Just specify the path.


Start Installation Notes

Any existing NetWare client is removed.  Specifically, the following NetWare clients are removed if found:

Novell NetWare (Workstation Shell 3.X (NETX))

Novell NetWare (Workstation Shell 4.0 and above (VLM))

Novell NetWare Client 32

[Microsoft] Client for NetWare Networks

[Microsoft] Service for NetWare Directory Services

NetWare Client 32 for Windows 95 is installed.

The Client 32 files are copied to your hard disk.

Insert the Client 32 diskettes as you are prompted for them.

Specify the path for the Windows 95 CAB files or for the Client 32 diskettes as necessary.

The folder for Client 32 is \Novell\Client32 on your workstation's Windows drive.  Some of the Client 32 files are copied to this folder.  Other files are copied to the appropriate Windows 95 folder, such as the \Windows\System, \Windows\Inf, and \Windows\Help folders.

The system registry is updated with the information needed to start Client 32 automatically each time Windows 95 starts.

Generally, the STARTNET.BAT, NET.CFG, and AUTOEXEC.BAT files are not created, modified, or used by Client 32.  If you are using 16-bit ODI LAN drivers, the AUTOEXEC.BAT and NET.CFG files are still used, but only by the 16-bit ODI LAN drivers.

Install checks for existing settings in the system registry and the NET.CFG file.  Any applicable settings found are moved to the registry.  For details, see Smart Defaults.

The installation program (SETUP.EXE) does not show up on the task bar.  You can use the Alt+Tab key combination, however, to quickly return to the installation program.  The Windows logo is used as its icon.


Support for Dial-Up Networking

Client 32 supports Windows 95 Dial-Up Networking.  If your workstation has a modem, ISDN network adapter, or connects to an X.25 network, install, configure, and use the Dial-Up Networking program that comes with Windows 95.

For more information about Dial-Up Networking, see the Microsoft Windows 95 Resource Kit.

Notes

When using Dial-Up Networking with Client 32, Dial-Up Networking uses the IPX 32-bit Protocol for Novell NetWare Client 32.

If, in addition to your modem or dial-up adapter, you also have a network adapter that is connected to a LAN, Client 32 attempts to log in to the LAN after the dial-up connection is made.  This allows you to regain your LAN connections after you make a dial-up connection.  However, this also prevents you from logging in using the dial-up connection.  In this case, you can use the dial-up connection for other connections (such as Internet access) but not for connecting to NetWare servers or trees.


Third-Party LAN Drivers

The following third-party LAN drivers are included in this Open Beta.

3C5X9.LAN

HP3AT16P.LAN

MADGEODI.LAN

SMC8000.LAN

SMC8100.LAN

OC32T164.LAN


To Change Your LAN Driver
Change the LAN Driver for Your Network Adapter

1  (Conditional) If you have not already run the install program (SETUP.EXE), run it.

2. (Conditional) If the Network control panel is not displayed, click here  [image] to display it.

3  Choose the network adapter that is installed.

4  Choose Remove.

5  (Conditional) If your network adapter is a Plug and Play adapter that Windows 95 detects and installs the software for, choose OK on the Network control panel and restart your computer.

OR

(Conditional) Otherwise, for ISA and MCA network adapters, choose Add, choose Adapter, choose Add, and select the LAN driver that you want.

Notes

After installing Client 32, when Windows 95 detects a Plug and Play adapter, it automatically installs an ODI LAN driver for the network adapter if an ODI LAN driver is available for the network adapter.

For Plug and Play adapters that Windows 95 detects and installs the software for, if you add a network adapter using the Network control panel, you might get two LAN drivers installed.  Therefore, you should let Windows 95 detect the network adapter and install the software for it, rather than doing it manually.

The new LAN driver is not used until after you restart your computer.

If an ODI LAN driver for your network adapter is already installed when you install Client 32, that LAN driver is used unless you change it.

If an NDIS LAN driver is already installed when you install Client 32 using SETUP.EXE, SETUP.EXE attempts to find a compatible ODI LAN driver.  If it finds one, SETUP.EXE replaces the NDIS driver with the ODI LAN driver.


To Print Help
Print Help

1  Choose Help Topics.

2  (Conditional) If the Contents tab isn't already displayed, choose Contents.

3  Choose the book that you want to print.

4  Choose Print.

5  Make sure the printer information is correct.

6  Choose OK.


To Remove ODINSUP
Remove ODINSUP and your adapter

1. Click here  [image] to display the Network control panel.

2  Choose Novell ODINSUP.

3  Choose Remove.

4  Choose on the name of your network adapter (for example, NE2000 Compatible).

5  Choose Remove.

6  Choose OK.

7  (Conditional)  If the Client 32 files or the Windows 95 CAB files are on a network drive, choose No.  Do not restart your computer, so you can access these files that are needed for installing Client 32.

OR

(Conditional)  Otherwise, choose Yes to restart your computer.


To run SETUP.EXE
Run SETUP.EXE

1  (Conditional) If you are installing from diskette, insert the Setup disk.

OR

(Conditional) If you are installing from CD-ROM, insert the NetWare Client 32 for Windows 95 CD-ROM.

2  (Conditional) If you are installing from a diskette in drive A:, click here [image] to run the installation program (SETUP.EXE).

OR

(Conditional) If you are not installing from a diskette in drive A:, run the SETUP.EXE program from the folder that has the Client 32 files.

Notes

The path to the Client 32 files cannot have any folders with long filenames in it.  All the folders in the path must conform to the 8.3 file naming convention.


Trademarks

Copyright © 1995, Novell, Inc.  All rights reserved.

Novell Trademarks

Novell, NetWare, DR DOS, and LANalyzer are registered trademarks of Novell, Inc. in the United States and other countries.

GroupWise, Internetwork Packet Exchange and IPX, IPX/SPX, ManageWise, NetWare 3, NetWare 4, NetWare Client, NetWare Core Protocol and NCP, NetWare Directory Services and NDS, NetWare DOS Requester, NetWare Loadable Module and NLM, NetWare Requester, NetWare/IP, Open Data-Link Interface and ODI, Packet Burst, Personal NetWare, Sequential Packet Exchange and SPX, and Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Novell Authorized Reseller is a service mark of Novell, Inc.

Third-Party Trademarks

AST is a registered trademark of AST Research, Inc.  Borland is a registered trademark of Borland International, Inc.  COMPAQ is a registered trademark of Compaq Computer Corporation.  CompuServe is a registered trademark of CompuServe Incorporated.  HP is a registered trademark of Hewlett-Packard Company.  IBM and OS/2 are registered trademarks of International Business Machines Corporation.  Intel is a registered trademark of Intel Corporation.  Microsoft, MS, MS-DOS, and Windows are registered trademarks, and Windows 95 is a trademark, of Microsoft Corporation.  Symantec and The Norton Utilities are registered trademarks of Symantec Corporation.  Unicode is a registered trademark of Transoft Ltd.


Unicode Files

All objects and their attributes in the NetWare 4 Directory database are stored in their Unicode (16-bit) representation.  However,clients use 256-character code pages (using 8-bit character codes).  The Unicode files are a set of Unicode translation tables needed to run NetWare utilities and manage the Directory database.

Notes

The appropriate Unicode files need to be in the Windows NLS folder (typically, C:\WINDOWS\NLS) or the Novell NetWare Client 32 NLS folder (typically, C:\NOVELL\CLIENT32\NLS).

The three-character extension for the Unicode files matches the DOS country code.

The Unicode files include the Windows code page file, the Windows code page to Unicode file, the Unicode monocasing file, and the Unicode collating file for your locale.

For example, the following Unicode files are for Germany:

1252_UNI.049 is used to translate code page 1252 to Unicode

UNI_1252.049 is used to translate Unicode to code page 1252

UNI_MON.049 is the monocasing file, which handles the proper alphabetization of upper- and lower-case letters

UNI_COL.049 is the collating file, which handles collation and sorted lists

For different code pages and locales, you need Unicode tables with corresponding code page numbers and country codes.


[MSTCP]

The properties (such as IPAddress) for the Microsoft TCP/IP protocol are specified in the [MSTCP] section.  This protocol (and hence this section) is needed for the NetWare/IP and SNMP features of Client 32.

If you are not using TCP/IP, NetWare/IP, or SNMP, this section is not needed.